home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-11
/
jbmake.zip
/
JBMAKE.DOC
< prev
next >
Wrap
Text File
|
1993-01-04
|
5KB
|
151 lines
8:13pm Feb 06,1989
Thank you for taking a look at jbMake. I hope it will be of use to you.
jbMake's origin is partially an outgrowth of my interest in C and a
frustration of trying to figure out how to use some of the make utilities
out there.
jbMake was designed originally for in house use, as such, it is biased
towards our programming standards, (if there is such a thing). As I have
time and the inclination I try and incorporate suggestion by my co-workers.
If you have suggestions to make jbMake better, please let me know and I
will do my best to contemplate them.
Features:
jbMake is written in 100% Turbo C. This makes it fairly fast.
jbMake is under 20k. I have tried to make it as lean as possible.
jbMake will catch changes made to *.prg(s) that are made under the
1 minute mark. This is great if you are using sidekick.
Drawbacks
jbMake does not support clip files (*.clp) at this time. However that
option will be forthcomming.
jbMake compiles each *.prg into its own *.obj. Depending on how you
normally compile, this may or may not be a drawback.
jbMake is for CLIPPER. It won't invoke other compilers.
And now for a little explanation.
A. Compiling
1. All of the systems we produce have a certain set of standards.
jbMake is designed to follow those standards, however there are ways
around this.
jbMake incorporates the -m switch for clipper. This produces a
single *.obj for each *.prg compiled. At this time this is the only
option supported by jbMake.
By default jbMake will compile all ??*.prg files in a directory,
where ?? is the first 2 characters of ??*.exe. That's just the way
we do it here.
Example: to compile files for vms.exe, jbMake vms
This will compile all vm*.prg files which have been
modified since the file VMS.EXE was created.
It will stop only after compiling all vm*.prg files which
have been modified, or after CLIPPER encounters an error.
To alter the compiling environment the following switches can be
thrown:
'o' jbMake vms -o, override naming conventions, this will compile
all *.prg files in the current directory that have been modified
since the last update of vms.exe
'i' jbMake vms -i, ignore any errors during the compile process.
This will compile all ??*.prg or *.prg files without stopping
after any compiler errors.
B. Linking
1. In order to link you MUST have a link file. Each linker has its own
syntax for its respective linkfile. I will assume you know how to
create that, if you don't, get a hold of me or someone else who can
help.
To link you will need to specify which linker you want to use by the
switch you throw:
't' for Tlink from Borland Int'l, the very fastest but no overlay
ability.
'm' for Link from MicroSoft, you need this if you are using Flipper
or some of the other libraries.
'p' for Plink86 from Phoenix, slow, slow, slow. But if your into
overlays...
Other link switches:
'w' wait after compiling before linking is started. I just threw
this option in for the heck of it.
'r' run the compiled and linked program after linking is finished.
C. Examples
1. jbMake vms
This will compile all vm*.prg(s) modified since vms.exe was created.
No linking will take place.
2. jbMake vms -tr This will compile all vm*.prg(s) modified since
vms.exe was created. jbMake will then link the file vms.lnk. After
linking, jbMake will execute the program vms.exe.
3. jbMake vms -otr
This will compile all *.prg(s) modified since vms.exe was created.
jbMake will then link the file vms.lnk. After linking jbMake will
execute the program vms.exe
4. jbMake vms -itrw
This will compile all vm*.prg(s) modified since vms.exe was created.
If any errors are detected they will be ignored. If no errors are
detected, jbMake will link the file vms.lnk. After linking jbMake
will wait for a keypress then execute the program vms.exe.
D. Installation:
1. You will need to put jbMake in a directory that is mapped to your
path.
2. Clipper and your linker must also be in a directory that is mapped to
your path.
3. Example:
If you put jbMake in C:\UTILITY, your path statement should include-
path=C:\UTILITY;C:\CLIPPER...
E. Future enhancements.
1. As I said earlier, jbMake basically used in-house. As I have the time
I am adding additions and enhancements to it. As far as future
enhancements go i can see:
a. redirection of errors to an error file.
b. compilation based on *.clp files
c. support of alternate *.lnk file names
d. support of clipper switches other than -m
2. I don't want jbMake to become so difficult to use it defeats its own
purpose. I am, therefore, intentionally trying to keep it as lean as
possible yet at the same time as powerful as possible.
3. If you've got some ideas please feel free to send them my way:
jeff d. bryant
4485 n. john albert
fresno, ca
93726